Hi @oskardotglobal, thanks for the PR. Can you give an example of how this would be used?

You could write your own network parsing logic and then pass it to morph like

# eval-machines.nix
import "${pkgs.morph.lib}/eval-machines.nix" {
  network = {}; # call whatever here
  networkExpr = null;
}

You could write your own network parsing logic and then pass it to morph like

# eval-machines.nix
import "${pkgs.morph.lib}/eval-machines.nix" {
  network = {}; # call whatever here
  networkExpr = null;
}

So just to clarify, it's for using eval-machines.nix outside of morph?
I'm not opposed to the change, it seems harmless no matter what, just looking to understand the use case better

it's for extending eval-machines